TRANSMIT SR BEFORE COMPLETING RACH

专利摘要:
to handle multiple ul access procedures, methods, apparatus and systems are revealed. an apparatus 300 includes a processor 305 and a transceiver 325 for communicating with a mobile communication network using a plurality of radio carriers. processor 305 initiates in 705 a first random access procedure for a first radio carrier. the processor 305 receives at 710 an escalation request activation for a second radio carrier while the first random access procedure remains pending. processor 305 determines in 715 whether simultaneous scheduling request transmission is allowed, in which transceiver 325 transmits in 720 a first scheduling request message to the second radio carrier in response to simultaneous scheduling request transmission.
公开号:BR112019023263A2
申请号:R112019023263-0
申请日:2018-05-07
公开日:2020-05-26
发明作者:Basu Mallick Prateek；Loehr Joachim；Kuchibhotla Ravi
申请人:Motorola Mobility Llc；
IPC主号:

专利说明:

TRANSMIT SR BEFORE COMPLETING RACK
FIELD
[001] The matter in question disclosed in this document concerns electronic communications and more particularly it concerns handling multiple UL access procedures.
BACKGROUND
[002] The abbreviations and acronyms set out below are thus defined, at least some of which are referred to in the description below.
[003] Third Generation Partnership Project (3GPP), Access and Mobility Management Function (AMF), Access Point Name (APN), Access Stratum (AS), Backoff Indicator (BI), Part Width Bandwidth (BWP), Carrier Aggregation (CA), Free Channel Assessment (CCA), Control Channel Element (CCE), Channel State Information (CSI), Common Search Space (CSS), Network Name Data (DNN), Radio Data Carrier (DRB), Downlink Link Control Information (DCI), Downlink Link (DL), Enhanced Free Channel Assessment (eCCA), Enhanced Broadband (eMBB), Node -B Evolved (eNB), Evolved Packet Core (EPC), ETS UMTS Terrestrial Radio Access Network (E-UTRAN), European Telecommunications Standardization Institute (ETSI), Frame Based Equipment (FBE), Division Duplexing Frequency (FDD), Frequency Division Multiple Access (FDMA), Temporary Globally Unique EU Identity (GUTI), Repeat Request Automatic Hybrid (HARQ), Domestic Subscriber Server (HSS),
Petition 870190113318, of 11/05/2019, p. 14/86
2/58
Internet of Things (ΙοΤ),
Key Indicators
Performance (KPI), Licensed Assisted Access (LAA), Charge Based Equipment (LBE), Listen Before You Speak (LBT), Long Term Evolution (LTE), Advanced LTE (LTE-A), Media Access Control ( MAC), Access
Multiple (MA), Schema (MCS), Type Communication (mMTC), Modulation Coding Management
Machine (MTC), Mass MTC
Mobility (MM),
Mobility Management (MME), Multiple Entries, Multiple Exits (MIMO), Multiple Path TCP (MPTCP), Shared Multiple User Access (MUSA), Non-Access Stratum (NAS), Narrow Band (NB), Network Function (NE), Next Generation (eg 5G) Node-B (gNB), Next Generation Radio Access Network (NG-RAN), New Radio (NR), Control & Charging Control (PCC), Guidelines Control (PCF), Policy Control and Billing Rules Function (PCRF), Convergence Protocol of
Packet Data (PCDP), Packet Data Network (PDN),
Packet Data Unit (PDU), PDN Communication Port (PGW), Quality of Service (QoS), Quadrature Phase Shift Switching (QPSK), Radio Access Network (RAN), Radio Access Technology (RAT), Radio Resource Control (RRC), Reception (RX), Switch / Split Function (SSF), Scheduling Request (SR), Server Communication Port (SGW), Session Management Function (SMF ), System Information (SI), System Information Block (SIB), Transport Block (TB), Transport Block Size (TBS), Division Duplexing
Petition 870190113318, of 11/05/2019, p. 15/86
3/58
Time (TDD), Time Division Multiplexing (TDM), Transmission and Reception Point (TRP), Transmission (TX), Uplink Control Information (UCI), Unified Data Management (UDM), Entity / Equipment User (Mobile Terminal) (UE), Uplink Link (UL), User Plan (UP), Universal Mobile Telecommunications System (UMTS), High Reliability and Low Latency Communications (URLLC) and Worldwide Interoperability for Micro Access -Waves (WiMAX).
[004] In some wireless communication systems, only one Random Access procedure can be in progress at any point in time on a MAC entity. If the MAC entity receives a request for a new Random Access procedure while another one is already in progress at the MAC entity, it depends on whether the UE implementation should continue with the procedure in progress or start with the new procedure.
SUMMARY
[005] Methods for handling multiple UL access procedures are revealed. Apparatus and systems also perform the functions of the methods. One method (for example, of a user device) for handling multiple UL access procedures includes initiating, by a remote unit, a first random access procedure for a first radio carrier and receiving a request activation on the remote unit for a second radio carrier while the first random access procedure remains pending. The first method also includes determining whether transmission of
Petition 870190113318, of 11/05/2019, p. 16/86
4/58 simultaneous scheduling request is allowed and transmitting, by the remote unit, a first scheduling request message to the second radio carrier to a mobile communication network in response to the simultaneous scheduling request transmission being allowed.
[006] Another method for handling multiple UL access procedures includes initiating, by a remote unit, a first random access procedure for a first radio carrier and receiving, on the remote unit, an escalation request activation for a second carrier radio while the first random access procedure remains pending. The second method includes transmitting, by the remote unit, a first escalation request message to the second radio carrier to a mobile communication network before completing the first random access procedure.
BRIEF DESCRIPTION OF THE DRAWINGS
[007] A more particular description of the modalities described above in a brief way will be rendered by reference to the specific modalities that are illustrated in the attached drawings. With the understanding that these drawings represent only a few modalities and that, therefore, they should not be considered as limiting the scope, the modalities will be described and explained with specificity and additional details through the use of the attached drawings, in which:
figure 1 is a schematic block diagram illustrating a modality of a communication system without
Petition 870190113318, of 11/05/2019, p. 17/86
5/58 wire to handle multiple UL access procedures;
figure 2 is a schematic block diagram illustrating an embodiment of a network procedure for handling multiple UL access procedures;
Figure 3 is a schematic block diagram illustrating an embodiment of a user equipment apparatus for handling multiple UL access procedures;
Figure 4 is a schematic block diagram illustrating an embodiment of a network equipment apparatus for handling multiple UL access procedures;
figure 5 is a diagram illustrating modalities of improved backoff indicators for handling multiple UL access procedures;
figure 6 is a flow chart illustrating a first embodiment of a method for handling multiple UL access procedures;
Figure 7 is a flow chart illustrating a second embodiment of a method for handling multiple UL access procedures; and figure 8 is a flow chart illustrating a third embodiment of a method for handling multiple UL access procedures.
DETAILED DESCRIPTION
[008] As will be perceived by those skilled in the art, aspects of the modalities can be incorporated as a system, apparatus, method or program product. Therefore, modalities can take the form of a totally hardware modality, a totally software modality (including firmware, resident software, microcode, etc.) or a modality combining aspects
Petition 870190113318, of 11/05/2019, p. 18/86
6/58 software and hardware.
[009] For example, the disclosed modalities can be implemented as a hardware circuit comprising customized very large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors or other distinct components. The revealed modalities can also be implemented in programmable hardware devices such as field programmable gate arrays, programmable arrangement logic, programmable logic devices or similar. As another example, the disclosed modalities may include one or more physical or logical blocks of executable code that can, for example, be organized as an object, procedure or function.
[010] In addition, modalities may take the form of a program product embedded in one or more computer-readable storage devices storing machine-readable code, computer-readable code and / or program code, hereinafter referred to as code . Storage devices can be tangible, non-transitory and / or non-transmitting. Storage devices may not incorporate signals. In a certain embodiment, storage devices employ only signals to access code.
[011] Any combination of one or more computer-readable media can be used. Computer-readable media can be computer-readable storage media. Computer-readable storage media can be a storage device
Petition 870190113318, of 11/05/2019, p. 19/86
7/58 storing the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical or semiconductor system, apparatus or device, or any suitable combination of those indicated above.
[012] More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable floppy disk, a hard disk, a random access memory (RAM), a memory read-only (ROM), a programmable and erasable read-only memory (EPROM or Flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the context of this document, a computer-readable storage medium can be any tangible medium that can contain or store a program for use by or in connection with a system, device or instruction execution device.
[013] Reference throughout this specification for a similar modality or language means that a particular structure, feature or resource described in connection with the modality is included in at least one modality. Thus, meanings of the phrase in a similar modality and language throughout this specification may all, but not necessarily, refer to the same modality, but mean one or more, but not all, unless specified
Petition 870190113318, of 11/05/2019, p. 20/86
8/58 expressly otherwise. The terms including, comprising, having and variations thereof mean including, but not limited to, unless expressly specified otherwise. An enumerated listing of items does not indicate that some or all of the items are mutually exclusive, unless expressly specified otherwise. The terms one, one, o and a also refer to one or more unless expressly specified otherwise.
[014] In addition, the structures, characteristics or resources described in the modalities can be combined in any appropriate way. In the following description, numerous specific details are provided, such as programming examples, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, chips hardware, etc., to provide a complete understanding of modalities. Those skilled in the art will recognize, however, that modalities can be practiced without one or more of the specific details, or with other methods, components, materials and so on. In other instances, well-known structures, operations or materials are not shown or described in detail to avoid obscuring aspects of a modality.
[015] Aspects of the modalities are described below with reference to schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems and program products according to modalities. It will be understood that each block of the schematic flowcharts and / or
Petition 870190113318, of 11/05/2019, p. 21/86
9/58 of the schematic block diagrams and block combinations in the schematic flowcharts and / or in the schematic block diagrams can be implemented using code. This code can be supplied to a processor for a general purpose computer, special purpose computer or other programmable data processing device to produce a machine, such that instructions, which are executed by means of the computer's processor or other programmable data processing apparatus, create resources to implement the functions / procedures specified in schematic flowcharts and / or schematic block diagrams.
[016] The code can also be stored on a storage device that can direct a computer, another programmable data processing device or other devices to function in a particular way, such that the instructions stored on the storage device produce a manufacturing article including instructions that implement the function / procedure specified in schematic flowcharts and / or schematic block diagrams.
[017] The code can also be loaded into a computer, another programmable data processing device or other devices to cause a series of operational steps to be performed on the computer, another programmable device or other devices to produce an implemented process by computer in such a way that the code that runs on the computer or on another programmable device provides processes to implement the functions / procedures
Petition 870190113318, of 11/05/2019, p. 22/86
10/58 specified in schematic flowcharts and / or schematic block diagrams.
[018] Schematic flowcharts and / or schematic block diagrams in the figures illustrate the architecture, functionality and operation of possible implementations of apparatus, systems, methods and program products according to various modalities. In this regard, each block in the schematic flowcharts and / or in the schematic block diagrams can represent a module, segment or part of code, which includes one or more executable instructions from the code to implement the logical function (s) ) specified.
[019] It should also be noted that, in some alternative implementations, the functions noted in the block may occur outside the order noted in the figures. For example, two blocks shown in succession, in fact, can be executed substantially concurrently, or the blocks can sometimes be executed in reverse order, depending on the functionality involved. Other steps and methods can be designed that are equivalent in function, logic or effect to one or more blocks, or parts thereof, of the illustrated figures.
[020] The description of elements in each figure can refer to elements in the following figures. Like numbers refer to like elements in all figures, including alternative modalities of like elements.
[021] In LTE, only one Random Access procedure can be in progress at any point in time on a MAC entity. If the MAC entity receives a request for a new Random Access procedure
Petition 870190113318, of 11/05/2019, p. 23/86
11/58 while another one is already underway at the MAC entity, it is up to the UE implementation to proceed with the ongoing procedure or start with the new procedure. In NR, a possible new reason for starting a RACH procedure may be to send the SI request message (method based on Msgl or Msg3). UE implementations aborting a corresponding RACH procedure to send IS request messages would risk delaying, among others, public safety, vehicle services and other critical services. For example, aborting the RACH procedure in Msgl may mean that the UE does not even send the reserved preamble (to request a corresponding SIB), but particularly expects the other RACH procedure to be completed - depending on the radio condition this can be a relatively long wait. big. However, aborting the RACH procedure in Msg3 may not be straightforward if the Msg3 grant size is different for SI requests and other purposes (for example, UL grant).
[022] To minimize delay, the UE can continue multiple RACH procedures in parallel when said RACH procedures are considered to be prioritized. An example is to initiate multiple RACH procedures, each for a different SI request. However, if RACH procedures are not considered to be prioritized, then the UE can cancel / abort the lower priority procedure (for example, request for non-SI). In a certain way, continuing multiple RACH procedures in parallel includes making multiple transmissions at the same time / slot / time frame.
[023] In some modalities, the multiple
Petition 870190113318, of 11/05/2019, p. 24/86
12/58 pending RACH procedures may have different priorities. Assume here that a second RACH procedure is activated while a first RACH procedure is already pending. Here, the UE can determine whether pending RACH procedures request system information (SI requests having a higher priority than other RACH procedures) and determine whether the required SIB is considered important or critical. Examples of important / critical SIBs include, but are not limited to, SIBs such as Commercial Mobile Alert System (CMAS), Wireless Emergency Alerts (WEA), Earthquake Warning System and Tsunami (ETWS), vehicle, public security or any other critical communication.
[024] If the first RACH procedure has already started and did not require an important / critical SIB, then the UE can cancel / abort the first RACH procedure and initiate a second RACH procedure to request SI, especially if the required SIBs are one of the SIBs important / critical. Note that if for the first RACH procedure the UE has already transmitted Msgl to request SIB (s), then the UE should not abort the first RACH procedure. In particular, the UE can send Msgl for the second RACH procedure at the next RACH opportunity, without waiting to complete the first RACH procedure.
[025] In some modalities, multiple pending RACH procedures may have the same priority. Assume again that the second RACH procedure is activated while the first RACH procedure is already pending. Here, multiple RACH procedures can be initiated to request SIBs where each (group of) SIB (s) is linked to a
Petition 870190113318, of 11/05/2019, p. 25/86
13/58
Corresponding preamble.
[026] If more than one STBs are required and belong to a different corresponding Preamble, then the UE can initiate a simultaneous Preamble transmission. However, in certain embodiments, the transmission power required for all such transmission is not available in the UE. Therefore, the UE can initiate Preamble transmission sequentially (for example, one by one). In this improvement, the UE initiates transmission of a subsequent Preamble at the next immediate RACH opportunity, for example, without having to wait to receive the response (Msg2) corresponding to a previous Preamble.
[027] In some modalities, the UE may receive more than one grant of Msg3 overlapping in time domain. In addition, the UE may not be able to transmit all Msg3s with the required power simultaneously (for example, based on the last increased Preamble transmission power). In such modalities, the UE can prioritize one RACH access over another. For example, an SI request can be prioritized over other Random accesses, in such a way that the UE uses the power required for the transmission of Msg3 corresponding to the prioritized RACH access and uses the remaining power for the other transmission of Msg3. Alternatively, the UE can use equal transmission power for all simultaneous Msg3 transmission. As another alternative, the UE can transmit Msg3 only to the highest priority RACH access and not send Msg3 transmission to the other RACH access.
[028] In certain modalities, the UE may prioritize a
Petition 870190113318, of 11/05/2019, p. 26/86
14/58 RACH access (as determined above) for an initial Msg3 transmission, but on retransmission opportunities (for example, if Asynchronous retransmission opportunities still collide) the UE prioritizes 'other' RACH access instead. In other modalities, the UE can use a weighting factor in proportion to its priorities to distribute power to each of the RACH accesses. Here, the network can control the configuration of such weighting factors.
[029] In some modalities, an Escalation Request (SR) is used for the UE to request upstream shared channel resources (UL-SCH) for new transmission. An SR configuration includes a set of PUCCH resources for SR across different parts of bandwidth (BWPs) and cells. Each SR configuration corresponds to one or more logical channels. Each logical channel can be mapped to zero or an SR configuration, for example, as configured by RRC. Only PUCCH resources in a BWP that are active at the time of the SR transmission time are considered valid.
[030] After sending an SR, the UE is expected to send a Temporary Storage Status Report (BSR). RAN uses BSR to scale an appropriately sized UL concession and the UE sends UL data in the concession. However, multiple transmission can cause undesirable / unacceptable delays for real data transmission for certain applications. To resolve this, in certain embodiments the UE can send UL data in place of the BSR, referred to in this document as direct data transmission.
Petition 870190113318, of 11/05/2019, p. 27/86
15/58
[031] Suppose the UE is configured with a Carrier A associated with URLLC service. In addition, the UE transmits data directly in place of a BSR to Carrier A, for example, as fixed by specification or configured by the network using RRC signaling on a UL grant received in response to a configured SR and subsequently activated for the Carrier A. In one embodiment, the UL grant activated for Carrier A can be used to directly transmit data to Carrier A if a dedicated SR is configured for Carrier A. In another embodiment, the UL grant activated for Carrier A can be used to directly transmit data to Carrier A if a dedicated SR is configured for Carrier A and the network has configured this carrier in such a way that a lease received in response to this SR (next lease received after the SR is sent) can only be used for data transmission from Carrier A. Here, temporary storage status report is not to be loaded into this UL concession unless data for Carrier A are already fully accommodated in the UL concession. Alternatively, the UE can use the UL grant for direct data transmission if a dedicated SR is configured for Carrier A and its logical channel priority is greater than a certain threshold, referred to as priority_threshold_low. If 'direct data transmission' is configured for certain carrier (s), then the UE can only consider data contained in the corresponding carrier (s) for transmission while executing the LCP (Channel Prioritization) procedure Logical).
Petition 870190113318, of 11/05/2019, p. 28/86
16/58
[032] In addition, in some embodiments, the UE can simultaneously execute SR procedure and RACH procedure for different logical channels. Here, consider a first radio carrier, Carrier A, for which SR is configured (for example, this carrier has PUCCH features configured for SR) and a second radio carrier, Carrier B, for which SR is not configured (for example, example, this carrier is not configured with PUCCH features for SR). When UL data arrives at Carrier B, a RACH procedure will be initiated since SR is not configured for Carrier B. If data at Carrier A arrives in the meantime, then the data at Carrier A, which may be for URLLC traffic, is delayed in an unacceptable way unless simultaneous / concurrent SR is possible. Therefore, the UE can activate and start SR and RACH procedures in parallel.
[033] In some modalities, the mobile communication network may wish to restrict the parallel SR and RACH procedures. To do this, it can configure whether the UE, or even certain UE carriers, is (or is not) authorized to activate parallel SR and RACH procedures. Alternatively, parallel SR and RACH procedures can be controlled using logical channel priority levels and a network-configured logical channel priority threshold. Here, carriers with lower priorities than the certain priority_threshold_high are not allowed to start a RACH procedure if an RACH / SR procedure is already in progress.
[034] Additionally, SR in NR may be specific to Carrier / Numerology and RACH may be required for others
Petition 870190113318, of 11/05/2019, p. 29/86
17/58 application data configured in a different Numerology for which an SR is not configured. However, in LTE, SR is EU specific; when an SR is configured the UE is not authorized to initiate a RACH procedure to apply for a UL grant. Applying EU-specific SR to NR can result in a data transmission starvation / delay for a carrier / service for which SR is not configured (for any of the Numerologies mapped to this carrier / service) over the network, especially if the Carrier / Numerology with configured SR resources is also configured for direct data transmission. Therefore, in several modalities the network configures carriers for the same group of logical channels (LCG) only if there is a common numerology (for example, subcarrier spacing) for carriers mapped to the LCG.
[035] Figure 1 represents a wireless communication system 100 for handling multiple UL access procedures, according to disclosure modalities. In one embodiment, the wireless communication system 100 includes at least one remote unit 105, an access network 120 containing at least two base units 110, wireless communication links 115 and a mobile primary network 140. Although a number specifics of remote units 105, access networks 120, base units 110, wireless communication links 115 and mobile main networks 140 are shown in figure 1, those skilled in the art will recognize that any number of remote units 105, access networks 120, base units 110, wireless communication links 115 and mobile main networks 140
Petition 870190113318, of 11/05/2019, p. 30/86
18/58 can be included in the wireless communication system 100. In another embodiment, access network 120 contains one or more WLAN access points (for example, Wi-Fi ™).
[036] In one implementation, the wireless communication system 100 is compatible with the 5G system specified in the 3GPP specifications. More generally, however, the wireless communication system 100 can implement any other open or proprietary communication network such as, for example, LTE or WiMAX, among other networks. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.
[037] In one embodiment, remote units 105 may include computing devices, such as desktop computers, laptops, personal digital assistants (PDAs), tablets, smartphones, smart TVs (for example, TVs connected to the Internet), smart devices (for example, devices connected to the Internet), signal-converting devices, game consoles, security systems (including security cameras), computers on board vehicles, network devices (for example, routers, switches, modems) or similar . In some embodiments, remote units 105 include wearable devices, such as smart watches, physical education bracelets, optical displays worn on heads or the like. In addition, remote units 105 can be referred to as subscriber units, mobile units, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, UE, user terminals, a device or by other terminology used in
Petition 870190113318, of 11/05/2019, p. 31/86
19/58 technique. Remote units 105 can communicate directly with one or more of the base units 110 via uplink (UL) and downlink (DL) communication signals. In addition, UL and DL communication signals can be loaded on wireless communication links 115.
[038] In some embodiments, remote units 105 can communicate with a remote host via a data path that passes through the main mobile network 140 and a data network 150. For example, a remote unit 105 can establish a PDU connection (or a data connection) to data network 150 via mobile main network 140 and access network 120. Mobile main network 140 then relays traffic between remote unit 105 and remote host using the PDU connection for data network 150.
[039] Base units 110 can be distributed in a geographical region. In certain embodiments, a base unit 110 can also be referred to as an access terminal, an access point, a base, a base station, a Node-B, an eNB, a gNB, a residence Node-B, a relay node, a device or by any other terminology used in the art. Base units 110 are generally part of a radio access network (RAN), such as access network 120, which may include one or more controllers communicatively coupled to one or more corresponding base units 110 . These and other elements of the radio access network are not illustrated, but are well known in general to people having common knowledge in the art. At
Petition 870190113318, of 11/05/2019, p. 32/86
20/58 base units 110 connect to the mobile main network 140 through access network 120.
[040] Base units 110 can serve multiple remote units 105 within a server area such as, for example, a cell or a cell sector via a wireless communication link 115. Base units 110 can communicate directly with one or more of the remote units 105 by means of communication signals. In general, the base units 110 transmit DL communication signals to serve the remote units 105 in the time, frequency and / or spatial domain. In addition, DL communication signals can be loaded onto wireless communication links 115. Wireless communication links 115 can be any suitable carrier in licensed or unlicensed radio spectrum. Wireless communication links 115 facilitate communication between one or more of the remote units 105 and / or one or more of the base units 110.
[041] In one embodiment, the mobile core network 140 is a 5G core (5GC) or an evolved packet core (EPC), which can be coupled to a data network 150, such as the Internet and private data networks , among other data networks. Each primary mobile network 140 may belong to a single public terrestrial mobile network (PLMN). The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.
[042] The main mobile network 140 includes several network functions (NFs). As shown, the main mobile network 140 includes multiple control plane functions
Petition 870190113318, of 11/05/2019, p. 33/86
21/58 including, but not limited to, an Access and Mobility Management Function (AMF) 143, a Session Management Function (SMF) 145 and a Policy Control Function (PCF). In addition, the main mobile network 140 includes a User Plan Function (UPF) 141 and a Unified Data Management (UDM) 147. Although specific numbers and types of network functions are represented in figure 1, those skilled in the art will recognize that any number and type of network functions can be included in the main mobile network 140.
[043] Methods, systems and devices for handling multiple UL access procedures are revealed in this document. Arrival of UL 125 data (for example, generated by an application running on remote unit 105) activates SR. If remote unit 105 is configured with PUCCH capabilities for SR, then remote unit 105 can send an SR 130 message. Otherwise, remote unit 105 initiates a RACH procedure in response to the arrival of UL 125 data. The base unit 110 identifies that remote unit 105 requires UL resources and submits the UL 135 grant.
[044] In some embodiments, UL 125 data arrives while another RACH procedure (for example, associated with a different carrier) is pending. To minimize delay, remote unit 105 can send the SR 130 message without waiting to complete the RACH procedure in progress, thus executing SR and RACH procedures in parallel. As mentioned above, simultaneous SR transmission may depend on a network configuration, a carrier configuration, a logical channel priority or the like.
Petition 870190113318, of 11/05/2019, p. 34/86
22/58
[045] Figure 2 represents a network procedure 200 for handling multiple UL access procedures, according to disclosure modalities. The network procedure 200 involves a UE 205 and a mobile communication network (MCN) 220. The UE 205 can be a mode of remote unit 105, described above. Additionally, MCN 220 can be a modality of access network 120 and mobile main network 140, described above. In various embodiments, the UE 205 interacts with a base unit 110 on MCN 220; for example, a gNB or other base station.
[046] Here, it is assumed that the UE 205 has established a first radio carrier (Carrier A 210) with MCN 220. In several modalities, the first radio carrier can include a first PDCP entity, one or more RLC entities associated with the first PDCP entity, and a first logical channel. It is also assumed that the UE 205 has established a second radio carrier (Carrier B 215). Similar to the first radio carrier, the second radio carrier can include a second PDCP entity, one or more RLC entities associated with the second PDCP entity, and a second logical channel. Where UE 205 is configured to use groups of logical channels, it is assumed that Carrier A 210 and Carrier B 215 are associated with different logical channel groups (thus reporting temporary storage status independently of each other).
[047] The network procedure 200 begins with the activation of a scheduling report (SR) on UE 205, the activated SR being associated with Carrier A 210 (see block 225). In response to the pending SR (e.g.,
Petition 870190113318, of 11/05/2019, p. 35/86
23/58 enabled), UE 205 determines whether PUCCH resources are configured for Carrier A 210 for the pending SR (for example, determines whether Carrier A 210's logical channel is mapped to an SR configuration). In the represented mode, it is assumed that Carrier A 210 is not mapped to an SR configuration, and thus the UE 205 determines that SR is not configured for Carrier A 210 (see block 230).
[048] Since no PUCCH resources are configured for Carrier A 210 for the pending SR, the UE 205 initiates a random access procedure (for example, RACH procedure) for the Carrier A 210 SR (see message 235). For example, the UE 205 can send a RACH Request in Msgl when starting the random access procedure.
[049] Additionally, while the RACH procedure for Carrier A 210 is pending, UE 205 also detects the activation of SR associated with Carrier B 215 (see block 240). In response to the pending SR (for example, enabled) for Carrier B 215, the UE 205 determines whether PUCCH resources are configured for Carrier B 215 for the pending SR (for example, determines whether the logical channel for Carrier B 215 is mapped for an SR configuration). In the represented mode, it is assumed that Carrier B 215 is mapped to an SR configuration, and thus the UE 205 determines which SR is configured for Carrier B 215 (see block 245).
[050] As there is a pending UL access procedure (for example, the RACH procedure for Carrier A 210), the UE 205 determines whether simultaneous SR transmission is
Petition 870190113318, of 11/05/2019, p. 36/86
24/58 authorized. For example, the UE 205 can determine whether simultaneous SR transmission is allowed on the mobile communication network 220, whether a logical channel priority of Carrier B 215 is sufficient to allow simultaneous SR transmission, and / or determine whether a configuration of Carrier B 215 allows simultaneous SR transmission. In addition, the UE 205 can determine whether an amount of transmit power is sufficient to simultaneously transmit messages for the RACH procedure for Carrier A 210 and the scheduling request message for Carrier B 215 in parallel. In the represented mode, it is assumed that simultaneous SR transmission is authorized (for example, allowed and sufficient transmission power is available, see block 250).
[051] As Carrier B 215 is mapped to an SR configuration, the UE 205 transmits an SR message to Carrier B 215 using configured PUCCH resources (see message 255). Note that the UE 205 transmits the SR message to Carrier B 215 before completing the RACH procedure for Carrier A 210. In the represented mode, the UE 205 receives a RACH response (for example, to Carrier A 210) at some point after transmitting the SR message to Carrier B 215 (see message 260).
[052] Although the modality represented assumes that Carrier A 210 has no SR configuration, in other modalities Carrier A 210 is configured with PUCCH resources for pending SR. In such modalities, the UE 205 may instead send an SR message to Carrier A 210, instead of initiating the RACH procedure for Carrier
Petition 870190113318, of 11/05/2019, p. 37/86
25/58
210, as shown. Here, the UE 2 05 can also send the SR message to Carrier B 215 before receiving a response to the SR message to Carrier A 210. In certain embodiments, the UE 205 can send SR messages to Carrier A 210 and to the Carrier B 215 in parallel.
[053] In addition, although the modality represented assumes that Carrier B 215 has an SR configuration, in other modalities Carrier B 215 is not configured with PUCCH resources for pending SR. In such embodiments, the UE 205 may instead initiate a second RACH procedure for Carrier B 215, instead of sending an SR message on configured PUCCH resources as represented. In certain embodiments, the UE 205 can initiate RACH procedures for Carrier A 210 and Carrier B 215 in parallel.
[054] Although the represented mode assumes that simultaneous SR transmission is authorized, in other modalities simultaneous SR transmission may not be authorized. In such modalities, the UE 205 can optionally cancel the RACH procedure for Carrier A 210 to send the SR message (or initiate a second RACH procedure) to Carrier B 215, for example, due to the logical channel priority of Carrier B 215 be greater than that of Carrier A 210. In certain modalities where simultaneous SR transmission is not authorized, the UE 205 may optionally delay the SR message (or second RACH procedure) to Carrier B 215 until the completion of the RACH procedure for Carrier A 210 , for example, due to carrier B 215 logical channel priority
Petition 870190113318, of 11/05/2019, p. 38/86
26/58 be equal to or less than that of Carrier A 210. Other modalities are also possible, as described in this document.
[055] Figure 3 represents a modality of a user equipment apparatus 300 that can be used to handle multiple UL access procedures, according to disclosure modalities. User equipment apparatus 300 may be a form of remote unit 105 and / or UE 205. In addition, user equipment apparatus 300 may include a processor 305, a memory 310, an input device 315, a device output 320 and a transceiver 325. In some embodiments, input device 315 and output device 320 are combined into a single device, such as a touch screen. In certain embodiments, the user equipment apparatus 300 does not include any input device 315 and / or output device 320.
[056] By means of transceiver 325, the user equipment apparatus 300 establishes at least two radio carriers. As discussed earlier, each radio carrier can be associated with a different logical channel. As shown, transceiver 325 includes at least one transmitter 330 and at least one receiver 335. In addition, transceiver 325 can support at least one network interface 340. Here, at least one network interface 340 facilitates communication with an eNB or gNB (for example, using the Uu interface). In addition, the at least one network interface 340 may include an interface used for communications with a UPF and / or AMF.
[057] The 305 processor, in one mode, can
Petition 870190113318, of 11/05/2019, p. 39/86
27/58 include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, processor 305 can be a microcontroller, a microprocessor, a central processing unit (CPU), a graphics processing unit (GPU), an auxiliary processing unit, an array of field programmable ports (FPGA) or controller similar programmable. In some embodiments, processor 305 executes instructions stored in memory 310 to execute the methods and routines described in this document. Processor 305 is communicatively coupled to memory 310, input device 315, output device 320 and transceiver 325.
[058] In several modalities, the 305 processor initiates a first UL access procedure for a first radio carrier. Here, the first UL access procedure can be a random access procedure, just like the RACH procedure discussed earlier. In other embodiments, the first UL access procedure can be an SR request transmitted on PUCCH resources configured for a logical channel associated with the first radio carrier.
[059] In addition, processor 305 can receive SR activation for a second radio carrier while the first UL access procedure request (eg, random access) remains pending. Here, SR activation can be the arrival of UL data associated with the second radio carrier. Note that it is assumed that the first and second radio carriers are not a part of the
Petition 870190113318, of 11/05/2019, p. 40/86
28/58 same group of logical channels. Thus, the second radio carrier reports its temporary storage status regardless of the first radio carrier.
[060] In such embodiments, processor 305 controls transceiver 325 to transmit a first SR message to the second radio carrier before completing the first uphill link access procedure. In some embodiments, processor 305 determines whether simultaneous SR transmission is allowed in response to receiving SR activation while the first UL access procedure remains pending. In certain modalities, simultaneous SR transmission is defined as allowed in the mobile communication network. In other embodiments, simultaneous SR transmission may be allowed if a logical channel priority of the second radio carrier is above a threshold level. In additional modes, simultaneous SR transmission can be allowed based on the configuration of the second radio carrier.
[061] In response to determining which simultaneous SR transmission is allowed, processor 305 controls transceiver 325 to transmit a first SR message to the second radio carrier. In various embodiments, processor 305 determines whether the second radio carrier is configured with PUCCH capabilities to transmit SR. Where PUCCH resources are configured for SR, then transmitting the first SR message to the second radio carrier includes transmitting an escalation request (for example, an uplink PHY layer message) using one of the configured PUCCH resources. Otherwise, if PUCCH resources are not configured for SR
Petition 870190113318, of 11/05/2019, p. 41/86
29/58 for the second radio carrier, then transmitting the first SR message to the second radio carrier may include initiating a RACH procedure (for example, transmitting a RACH Request in Msgl).
[062] In some embodiments, determining whether simultaneous SR transmission is allowed may include the 305 processor identifying a logical channel priority associated with the second radio carrier. In addition, processor 305 can compare the logical channel priority of the second radio carrier to a priority threshold, where processor 305 determines that simultaneous SR transmission is allowed if the logical channel priority exceeds the priority threshold.
[063] As mentioned, in certain embodiments the processor 305 uses a second radio carrier configuration to determine whether simultaneous escalation request transmission is allowed. In other embodiments, the mobile communication network defines simultaneous scheduling request transmission as being allowed and, therefore, processor 305 can always determine that simultaneous SR is allowed.
[064] Where simultaneous SR transmission is allowed, processor 305 can determine whether an amount of transmit power is sufficient to simultaneously transmit messages for the first UL access procedure and the first SR message in parallel. In certain embodiments, transmitting the first escalation request message to the second radio carrier may include reducing the power of a lower priority message from the first and second radio carrier
Petition 870190113318, of 11/05/2019, p. 42/86
30/58 radio carrier.
[065] In some embodiments, processor 305 determines a first logical channel priority of the first radio carrier and a second logical channel priority of the second radio carrier in response to the simultaneous scheduling request transmission not being allowed and cancels the first UL access procedure in response to the first logical channel priority is less than the second logical channel priority. For example, if simultaneous SR transmission is not allowed, then processor 305 can determine to cancel the first UL access procedure to avoid delaying the first SR message. Advantageously, this allows SR messages associated with critical services, such as public security, telematics / vehicle control, emergency alerts and the like, to have priority over other services.
[066] In certain embodiments, processor 305 may receive (for example, via transceiver 325) an uplink grant for a temporary storage status report in response to the first SR message. In such embodiments, processor 305 can optionally send uplink data in lieu of a temporary storage status report at the concession. In certain embodiments, processor 305 may select an appropriate MAC control element (CE) subheader to indicate that uplink data is sent in place of the staging status report.
[067] In some embodiments, the 305 processor can
Petition 870190113318, of 11/05/2019, p. 43/86
31/58 receive (for example, via transceiver 325) a backoff indicator message. As understood in the art, a backoff indicator prohibits any RACH attempts for an indicated amount of time. In such embodiments, the backoff indicator message may include one or more service identifier fields. Here, processor 305 initiates a backoff timer for an amount of time based on the backoff indicator message only for the specific service (s) indicated by the service identifier field. In one embodiment, the service identifier field is a positive list in which a backoff timer is started for the identified service (s). In another embodiment, the service identifier field is a negative list in which a backoff timer is started for all services with the exception of the identified service (s). In addition, in various embodiments, the backoff indicator message may include a plurality of service identifier fields.
[068] In some embodiments, processor 305 receives an activation for a first RACH request, while a second RACH procedure is pending. Here, processor 305 can identify a first priority from the first RACH request and second priority from the second RACH procedure. If both the first priority and the second priority are high, then processor 305 can control transceiver 325 to transmit the first RACH request before the completion of the second RACH procedure. In one embodiment, a RACH message requesting an STB can be considered to have a high priority,
Petition 870190113318, of 11/05/2019, p. 44/86
32/58 while a RACH message requesting a transfer grant can be considered to have a lower priority. In another embodiment, only a RACH message requesting a critical service SIB can be considered to have a high priority. Critical services here may include, but are not limited to, emergency alerts (for example, Mobile Commercial Alert System (CMAS), Wireless Emergency Alerts (WEA), Earthquake and Tsunami Warning System (ETWS) or other disaster reporting systems), vehicle control / telematics and public security services.
[069] In certain embodiments, the 305 processor can abort (cancel) the second (for example, already pending) RACH procedure, for example, in response to the first priority being high and the second priority being low. In other embodiments, processor 305 may delay transmission of the first RACH request until completion of the second RACH procedure.
[070] In some modalities, the first priority and the second priority may have the same priority level. In such embodiments, processor 305 can identify a next RACH opportunity and control transceiver 325 to transmit the first RACH request comprises transmitting during the next RACH opportunity, even if the next RACH opportunity arises before receiving a response for the second random access procedure.
[071] In certain embodiments, transmitting the first RACH request includes simultaneously transmitting a first RACH preamble corresponding to the first
Petition 870190113318, of 11/05/2019, p. 45/86
33/58 RACH request and a second RACH preamble corresponding to the second pending RACH procedure. In addition, processor 305 can receive a first RACH response corresponding to the first RACH request and a second RACH response corresponding to the second RACH procedure, each RACH response including a RACH grant, in which the RACH leases overlap over time. In such embodiments, processor 305 may reduce a third RACH message transmission power to a lower priority of the first RACH request and the second RACH procedure due to overlapping RACH leases over time.
[072] In one embodiment, processor 305 can reduce the transmit power of a retransmission opportunity from the lowest priority of the first RACH request and the second RACH procedure in response to reducing the transmit power of the third RACH message to the highest priority download of the first RACH request and the second RACH procedure. In certain embodiments, a power reduction amount of the third message is based on a weighting factor. Here, the weighting factor can be selected based on the relative priority of the first priority compared to the second priority.
[073] Memory 310, in one embodiment, is a computer-readable storage medium. In some embodiments, memory 310 includes volatile computer storage media. For example, memory 310 may include RAM, including dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM) and / or static RAM (SRAM). In
Petition 870190113318, of 11/05/2019, p. 46/86
34/58 In some embodiments, memory 310 includes non-volatile computer storage media. For example, memory 310 may include a hard disk drive, flash memory or any other suitable non-volatile computer storage device. In some embodiments, memory 310 includes both volatile and non-volatile computer storage media. In some embodiments, memory 310 stores data relating to handling multiple UL access procedures, for example, storing carrier configurations, SR configurations, logical channel priorities, backoff indicators and the like. In certain embodiments, memory 310 also stores program code and related data, such as an operating system or other controller algorithms operating on user equipment apparatus 300 and one or more software applications.
[074] The input device 315, in one embodiment, can include any known computer input device including a touch panel, a key, a keyboard, a pointer, a microphone or the like. In some embodiments, the input device 315 can be integrated with the output device 320, for example, as a touchscreen or similar touchscreen. In some embodiments, the input device 315 includes a touchscreen in such a way that text can be entered using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, the input device 315 includes two or more devices
Petition 870190113318, of 11/05/2019, p. 47/86
35/58, such as a keyboard and touch panel.
[075] The output device 320, in one embodiment, can include any known electronically controllable display or display device. Output device 320 can be designed to produce visual, audible and / or tactile signals. In some embodiments, the output device 320 includes an electronic display capable of producing visual data for a user. For example, output device 320 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector or similar display device capable of producing images, text or the like for a user . As another non-limiting example, output device 320 may include a wearable display such as a smart watch, smart glasses, a head-up display or the like. Additionally, output device 320 may be a component of a smartphone, personal digital assistant, television, tablet, notebook (laptop), personal computer, vehicle panel or the like.
[076] In certain embodiments, the output device 320 includes one or more speakers to produce sound. For example, output device 320 can produce an audible alert or notification (for example, a beep or bell). In some embodiments, the output device 320 includes one or more tactile devices to produce vibrations, movement or other tactile feedback. In some embodiments, all or some parts of the output device 320 can be integrated with the input device
Petition 870190113318, of 11/05/2019, p. 48/86
36/58
315. For example, the input device 315 and the output device 320 can form a touch screen or similar touch screen. In other embodiments, all or some parts of the output device 320 may be located close to the input device 315.
[077] Transceiver 325 communicates with one or more network functions of a mobile communication network. Transceiver 325 operates under the control of processor 305 to transmit messages, data and other signals and also to receive messages, data and other signals. For example, processor 305 can selectively activate the transceiver (or parts thereof) at particular times in order to send and receive messages. Transceiver 325 may include one or more transmitters 330 and one or more receivers 335.
[078] Figure 4 represents a modality of a network equipment apparatus 400 that can be used to handle multiple UL access procedures, according to disclosure modalities. The network equipment apparatus 400 may be a form of the base unit 110 and / or gNB 210. In addition, the network equipment apparatus 400 may include a processor 405, a memory 410, an input device 415, a output device 420 and a transceiver 425. In some embodiments, input device 415 and output device 420 are combined into a single device, such as a touchscreen. In certain embodiments, the network equipment apparatus 400 does not include any input device 415 and / or output device 420.
[079] As shown, the 425 transceiver includes
Petition 870190113318, of 11/05/2019, p. 49/86
37/58 at least one transmitter 430 and at least one receiver 435. In addition, transceiver 425 can support at least one network interface 440. Here, at least one network interface 440 facilitates communication with a remote unit 105, such as UE 205, and with other network functions on a mobile main network 140, such as UPF 141, AMF 143 and the like.
[080] The 405 processor, in one embodiment, can include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, processor 405 can be a microcontroller, a microprocessor, a central processing unit (CPU), a graphics processing unit (GPU), an auxiliary processing unit, an array of field programmable ports (FPGA) or controller similar programmable. In some embodiments, processor 405 executes instructions stored in memory 410 to execute the routines and methods described in this document. Processor 405 is communicatively coupled to memory 410, input device 415, output device 420 and transceiver 425.
[081] In several embodiments, processor 405 establishes at least two radio bearers to communicate with a UE, such as the UE 205. Here, each radio bearer can include a PDCP protocol entity, at least one protocol entity RLC associated with said PDCP protocol entity, and an associated logical channel. In certain embodiments, the 405 processor can configure a radio carrier with PUCCH capabilities to
Petition 870190113318, of 11/05/2019, p. 50/86
38/58 transmit SR.
[082] In some embodiments, the 405 processor receives a UL access request from a UE. Here, the UL access request can be an SR send in configured PUCCH resources or a RACH procedure. In response to the UL access request, the 405 processor can then escalate UL resources to the UE to send a temporary storage status report and indicate the UL resources when sending a UL grant message to the UE. In certain embodiments, the 405 processor can receive UL data at the UL grant in place of the temporary storage status report. In one embodiment, a MAC CE subheader associated with the UL grant indicates that the UE is sending UL data instead of a staging status report.
[083] In some embodiments, the 405 processor may send a backoff indicator message to the UE in response to the UL access request. In such embodiments, the backoff indicator message may include one or more service identifier fields. Here, processor 405 identifies one or more specific services using the service identifier field. Upon receiving the backoff indicator message, the UE mimics a backoff timer.
[084] In one embodiment, the service identifier field is a positive list in which a backoff timer is started for the identified service (s). In another embodiment, the service identifier field is a negative list in which a backoff timer is started for all services with the exception of the identified service (s). In addition, in several modalities, the message indicating
Petition 870190113318, of 11/05/2019, p. 51/86
39/58 backoff can include a plurality of service identifier fields.
[085] Memory 410, in one mode, is a computer-readable storage medium. In some embodiments, memory 410 includes volatile computer storage media. For example, memory 410 may include RAM, including dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM) and / or static RAM (SRAM). In some embodiments, memory 410 includes non-volatile computer storage media. For example, memory 410 may include a hard disk drive, flash memory or any other suitable non-volatile computer storage device. In some embodiments, memory 410 includes both volatile and non-volatile computer storage media. In some embodiments, memory 410 stores data relating to handling multiple UL access procedures; for example, storing carrier configurations, SR configurations, backoff indicators and the like. In certain embodiments, memory 410 also stores program code and related data, such as an operating system or other controller algorithms operating on the network equipment 400 and one or more software applications.
[086] Input device 415, in one embodiment, can include any known computer input device including a touch panel, a key, a keyboard, a pointer, a microphone or the like. In some embodiments, the input device 415 can be integrated with the output device 420, for example, as
Petition 870190113318, of 11/05/2019, p. 52/86
40/58 a touchscreen or similar touchscreen. In some embodiments, the input device 415 includes a touchscreen in such a way that text can be entered using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, the input device 415 includes two or more different devices, such as a keyboard and a touch panel.
[087] The output device 420, in one embodiment, may include any known electronically controllable display or display device. Output device 420 can be designed to produce visual, audible and / or tactile signals. In some embodiments, the output device 420 includes an electronic display capable of producing visual data for a user. For example, the output device 420 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector or similar display device capable of producing images, text or the like for a user . As another non-limiting example, output device 420 may include a wearable display such as a smart watch, smart glasses, a head-up display or the like. Additionally, the output device 420 can be a component of a smartphone, personal digital assistant, television, tablet, notebook (laptop), personal computer, vehicle panel or the like.
[088] In certain embodiments, the output device 420 includes one or more speakers to produce sound. Per
Petition 870190113318, of 11/05/2019, p. 53/86
41/58 example, output device 420 may produce an audible alert or notification (for example, a beep or bell). In some embodiments, the output device 420 includes one or more tactile devices to produce vibration, movement or other tactile feedback. In some embodiments, all or some parts of the output device 420 can be integrated with the input device 415. For example, the input device 415 and the output device 420 can form a touch screen or similar touch screen. In other embodiments, all or some parts of the output device 420 can be located close to the input device 415.
[089] Transceiver 425 operates under the control of processor 405 to transmit messages, data and other signals and also to receive messages, data and other signals. For example, the 405 processor can selectively activate the transceiver (or parts of it) at particular times in order to send and receive messages. Transceiver 425 may include one or more transmitters 430 and one or more receivers 435.
[090] Figure 5 represents several modalities of improved backoff indicator messages, according to the disclosure modalities. In certain embodiments, the enhanced backoff indicator messages form part of a MAC header or sub-header. Here, an LTE 500 backoff indicator message is represented having a plurality of fields (having an 'E / T / R / R / BI' format). The Έ 'field is a 1-bit field that indicates whether or not there is another sub-header following the present sub-header.
Petition 870190113318, of 11/05/2019, p. 54/86
42/58
For example, a value of '1' may indicate that there is at least one following subheader, while a value of '0' may indicate that there are no more subheadings, indicating that the next byte is the starting byte of MAC SDU or MAC CE or Filling. The 'Τ' field (type field) is a 1-bit field that can be used to distinguish a backoff indicator message from another MAC header / sub-header. For example, in LTE the field 'Τ' is used to distinguish a subheader containing a backoff indicator from a subheader containing a Random Access ID. The 'R' fields are reserved in LTE and the 'BI' field (backoff indicator field) is a 4-bit field that indicates an amount of time the UE is to wait before starting a RACH procedure.
[091] As 5G networks are expected to serve different verticals, for example, supporting different network slices that reserve appropriate resources on the network, different verticals or services may have different requirements and different QOS characteristics (referred to as '5QI'), including priorities and the possibility of preemption. Additionally, a mobile communication network has a certain capacity of how many UEs (charge) it can handle and when loaded it may need to take appropriate action including blocking certain UEs (for example, Access Classes), prohibit RACH access, release some Connected UEs in RRC, etc. A mechanism to prohibit RACH access is to send a backoff indicator, inducing the UE to stop any RACH attempts during a certain Backoff timer. In 5G, however, for some verticals / services it is very important to minimize delay.
Petition 870190113318, of 11/05/2019, p. 55/86
43/58
[092] In a first 505 enhanced backoff indicator message, the reserved fields of the LTE message are replaced by a Service ID ('SID') field used to identify a particular service associated with the backoff indicator. In various modalities, the UE does not use backoff for all services simultaneously in response to the backoff indicator message / subheader, but instead starts a backoff timer for the identified service. In the first enhanced backoff indicator message 505 the SID field is a 2-bit field that can signal up to four different services. Upon reading the first 505 enhanced backoff indicator message, the UE notes that the type field ('Τ') indicates a backoff indicator and reads the next two bits to identify the backoff service.
[093] In the second enhanced backoff indicator 510 and the third enhanced backoff indicator 515, the 'Τ' field and a reserved field of the LTE message are replaced by an extended type field ('Extended T'). Here, the extended type field is a 2-bit field that can signal up to four different meanings. A first value can be used to indicate that the MAC subheader contains a Random Access ID. A second value can be used to indicate that the MAC subheader contains a backoff indicator for all services (for example, no SID included). A third value can be used to indicate that the MAC subheader contains a backoff indicator and a positive list of SIDs. A fourth value can be used to indicate that the MAC subheader contains a backoff indicator and a negative list of SIDs. Such as
Petition 870190113318, of 11/05/2019, p. 56/86
44/58 used here, a positive list means that the backoff indicator is applicable for each service listed, while a negative list means that the backoff indicator is applicable for all services except those listed.
[094] Note that the backoff indicator messages with lists of SIDs comprise two or more bytes. Here, the second enhanced backoff indicator 510 and the third enhanced backoff indicator 515 are two-byte messages with the SID lists occupying one byte. In addition, the SID field can be of any suitable size. In the second improved backoff indicator 510 each SID field is a 2-bit field used to identify one of up to four different services. In the third enhanced backoff indicator 515 each SID field is a 4-bit field used to identify one of up to 16 different services.
[095] The improved backoff indicator revealed is not to be limited to the examples represented. In some embodiments, the SID field is used to indicate an Access Reason Identifier instead of a specific service. For example, a first value can correspond to a beam failure recovery request, a second value can correspond to a URLLC application and a third value can correspond to an SI request, with the fourth value being applicable for all other reasons access. In an additional example, the mobile communication network can be configured to never back out of a beam failure recovery request, URLLC application or SI request. In a situation like this, a value in the SID field can then
Petition 870190113318, of 11/05/2019, p. 57/86
45/58 correspond to eMBB data. In other examples, the SID field may apply to other categories of services / applications.
[096] In certain modalities, the value in the 'BI' field (backoff indicator field) can be applied differently for different services, applications or reasons for access. For example, the SIB may indicate scaling factors applicable for different services / applications / access reasons. Here, the scale factor can be applied to the backoff indicator to shorten or extend the backoff time. In other modalities, separate backoff indicator messages / subheadings can be sent so that different services / applications / access reasons are indented differently.
[097] Figure 6 represents a 600 method for handling multiple UL access procedures, according to disclosure modalities. In some embodiments, method 600 is performed by a remote unit, such as remote unit 105, UE 205 and / or user equipment apparatus 300, described above. In some embodiments, method 600 is executed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA or the like.
[098] Method 600 starts and starts in 605 a first random access procedure for a first radio carrier. Here, the first radio carrier can be associated with a first logical channel and report its temporary storage status regardless of
Petition 870190113318, of 11/05/2019, p. 58/86
46/58 a second radio carrier. Method 600 includes receiving 610 SR activation for the second radio carrier while the first random access procedure remains pending.
[099] Method 600 includes transmitting in 615, to a mobile communication network, a first SR message to the second radio carrier before completing the first random access procedure. Method 600 ends. In one embodiment, the second radio carrier is configured with PUCCH resources for pending SR. Here, transmitting the first SR message in 615 includes sending the escalation request on the configured PUCCH resources. In another mode, the second radio carrier is not configured with PUCCH resources for pending SR. Here, transmitting the first SR message at 615 includes starting a second random access procedure.
[0100] Figure 7 represents a method 700 for handling multiple UL access procedures, according to disclosure modalities. In some embodiments, method 7 00 is performed by a remote unit, such as remote unit 105, UE 205 and / or user equipment apparatus 300, described above. In some embodiments, method 700 is executed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA or similar
[0101] Method 700 begins and starts in 705 a first random access procedure for a first radio carrier. Here, the first radio carrier can be associated with a first logical channel and report
Petition 870190113318, of 11/05/2019, p. 59/86
47/58 its temporary storage status regardless of a second radio carrier. Method 700 includes receiving at 710 an SR activation for the second radio carrier while the first random access procedure remains pending. Here, SR activation may be due to receiving UL data for the second radio carrier.
[0102] Method 700 includes determining in 715 whether simultaneous SR is allowed. In one embodiment, the mobile communication network defines simultaneous SR transmission as being allowed. In other modalities, determining in 715 whether simultaneous SR transmission is allowed is based on a configuration of the second radio carrier. In certain embodiments, determining in 715 whether simultaneous SR transmission is permitted comprises identifying a logical channel priority associated with the second radio carrier. Here, simultaneous SR transmission can be allowed if the logical channel priority exceeds a priority threshold.
[0103] Method 700 includes transmitting in 720, to a mobile communication network, a first SR message to the second radio bearer before completing the first random access procedure in response to the simultaneous scheduling request transmission being allowed. Method 700 ends. In some embodiments, transmitting the first SR message to the second radio carrier at 720 may include reducing the power of a lower priority message from the first radio carrier and the second radio carrier. For example, the device can determine whether an amount of transmit power is sufficient to simultaneously transmit messages for the first random access procedure
Petition 870190113318, of 11/05/2019, p. 60/86
48/58 and the first parallel scheduling request message and reduce the message power with the lowest priority based on the determination.
[0104] In one mode, the second radio carrier is configured with PUCCH resources for pending SR. Here, transmitting the first SR message in 720 includes sending the escalation request on the configured PUCCH resources. In another mode, the second radio carrier is not configured with PUCCH resources for pending SR. Here, transmitting the first SR message at 720 includes starting a second random access procedure.
[0105] Figure 8 represents an 800 method for handling multiple UL access procedures, according to disclosure modalities. In some embodiments, method 800 is performed by a remote unit, such as remote unit 105, UE 205 and / or user equipment apparatus 300, described above. In some embodiments, method 800 is performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA or the like.
[0106] Method 800 starts and receives in 805 an activation for a first RACH request, while a second RACH procedure is pending. In one embodiment, activation for a first RACH request is due to the arrival of UL data. In another embodiment, the first RACH request is a request for System Information, for example, to request a SIB.
[0107] Method 800 includes identifying in 810 a first priority of the first RACH request and second
Petition 870190113318, of 11/05/2019, p. 61/86
49/58 priority of the second RACH procedure. In certain embodiments, a request for a SIB has a higher priority than that of another type of RACH request. In some modalities, the first priority and the second priority have the same level of priority.
[0108] Method 800 includes transmitting in 815 the first RACH request before the completion of the second RACH procedure in response to both the first priority and the second priority being high. Method 800 ends. In some embodiments, transmitting the first RACH request in 815 includes transmitting the first RACH request during an upcoming RACH opportunity before receiving a response to the second random access procedure. In certain embodiments, transmitting in 815 the first RACH request includes simultaneously transmitting a first RACH preamble corresponding to the first RACH request and a second RACH preamble corresponding to the second pending RACH procedure.
[0109] A first device for handling multiple UL access procedures is disclosed in this document. The first apparatus includes a processor and a transceiver that communicates with a mobile communication network using a plurality of radio carriers. The processor initiates a first random access procedure for a first radio carrier and receives an escalation request activation for a second radio carrier while the first random access procedure remains pending. In addition, the processor determines whether simultaneous scheduling request transmission is allowed, and the transceiver
Petition 870190113318, of 11/05/2019, p. 62/86
50/58 transmits a first scheduling request message to the second radio carrier in response to the simultaneous scheduling request transmission being allowed.
[0110] In certain modalities of the first device, determining whether simultaneous scheduling request transmission is permitted comprises identifying a logical channel priority associated with the second radio carrier. In such embodiments, the first apparatus may include comparing the logical channel priority associated with the second radio carrier to a first priority threshold, where simultaneous escalation request transmission is allowed if the logical channel priority exceeds the first threshold of priority.
[0111] In certain modalities of the first device, determining whether simultaneous scheduling request transmission is allowed is based on a configuration of the second radio carrier. In other modalities of the first device, the mobile communication network can define simultaneous scheduling request transmission as being allowed.
[0112] In some embodiments of the first device, the processor determines whether an amount of transmission power is sufficient to simultaneously transmit messages for the first random access procedure and the first parallel scheduling request message, in response to the request transmission simultaneous scheduling is allowed. In such modalities of the first device, transmit the first scheduling request message to the second carrier
Petition 870190113318, of 11/05/2019, p. 63/86
Radio 51/58 comprises reducing the power of a message of a lower priority from the first radio carrier and the second radio carrier.
[0113] In some embodiments of the first device, the processor determines a first logical channel priority of the first radio carrier and a second logical channel priority of the second radio carrier in response to the simultaneous scheduling request transmission not being allowed and cancels the first random access procedure in response to the first logical channel priority is less than the second logical channel priority.
[0114] In several modalities of the first device, the second radio carrier is not configured with any PUCCH resource for the first escalation request message. In such modalities, transmitting the first escalation request message comprises initiating a second random access procedure. In some embodiments of the first device, the processor receives a temporary storage status report for a temporary storage status report in response to the first escalation request message and controls the transceiver to transmit uplink data in the data concession. temporary storage status report.
[0115] In some modalities of the first device, the processor receives a backoff indicator message, the backoff indicator message including a service identifier field and starting a backoff timer for a specific service for a specified amount of time.
Petition 870190113318, of 11/05/2019, p. 64/86
52/58 based on the backoff indicator message. In various embodiments of the first device, the backoff indicator message includes a plurality of service identifier fields. In certain modalities, the backoff indicator is applied for each service identified in the plurality of service identifier fields. In other modalities, the backoff indicator is applied to all services except those identified in the plurality of service identifier fields.
[0116] A first method for handling multiple UL access procedures is disclosed in this document. The first method includes initiating, by a remote unit, a first random access procedure for a first radio carrier and receiving, on the remote unit, an escalation request activation for a second radio carrier while the first random access procedure remains pending. The first method also includes determining whether simultaneous escalation request transmission is allowed and transmitting, by the remote unit, a first escalation request message to the second radio carrier to a mobile communication network in response to the simultaneous escalation request transmission. be allowed.
[0117] In certain modalities of the first method, determining whether simultaneous scheduling request transmission is permitted comprises identifying a logical channel priority associated with the second radio carrier. In such embodiments, the first method may include comparing the logical channel priority associated with the second radio carrier to a first
Petition 870190113318, of 11/05/2019, p. 65/86
53/58 priority threshold, where simultaneous scheduling request transmission is allowed if the logical channel priority exceeds the first priority threshold.
[0118] In certain modalities of the first method, determining whether simultaneous scheduling request transmission is allowed is based on a configuration of the second radio carrier. In other modalities of the first method, the mobile communication network can define simultaneous scheduling request transmission as being allowed.
[0119] In some embodiments, the first method also includes determining whether an amount of transmit power is sufficient to simultaneously transmit messages for the first random access procedure and the first parallel scheduling request message, in response to the request transmission simultaneous scheduling is allowed. In such embodiments of the first method, transmitting the first escalation request message to the second radio carrier comprises reducing the power of a lower priority message from the first radio carrier and the second radio carrier.
[0120] In some embodiments, the first method includes determining a first logical channel priority for the first radio carrier and a second logical channel priority for the second radio carrier in response to the simultaneous scheduling request transmission not being allowed and canceling the first random access procedure in response to the first logical channel priority being lower than the second logical channel priority.
Petition 870190113318, of 11/05/2019, p. 66/86
54/58
[0121] In several modalities of the first method, the second radio carrier is not configured with any PUCCH resource for the first escalation request message. In such modalities, transmitting the first escalation request message comprises initiating a second random access procedure. In some embodiments, the first method includes receiving a temporary storage status report grant for a temporary storage status report in response to the first escalation request message and transmitting uphill link data in the storage status report grant temporary.
[0122] In some embodiments, the first method includes receiving a backoff indicator message, the backoff indicator message including a service identifier field and starting a backoff timer for a specific service for an amount of time based on the indicator message backoff. In various embodiments of the first method, the backoff indicator message includes a plurality of service identifier fields. In certain modalities, the backoff indicator is applied to each service identified in the plurality of service identifier fields. In other modalities, the backoff indicator is applied to all services except those identified in the plurality of service identifier fields.
[0123] A second method for handling multiple UL access procedures is disclosed in this document. The second method includes initiating, by a remote unit, a first random access procedure for a first
Petition 870190113318, of 11/05/2019, p. 67/86
55/58 radio bearer and receive, on the remote unit, an escalation request activation for a second radio bearer while the first random access procedure remains pending. The second method includes transmitting, by the remote unit, a first escalation request message to the second radio carrier to a mobile communication network before completing the first random access procedure.
[0124] In certain embodiments, the second method includes determining which simultaneous escalation request transmission is allowed before transmitting the first escalation request message. In one embodiment, a logical channel priority from the second radio carrier indicates that simultaneous scheduling request transmission is allowed. In another embodiment, a second radio carrier configuration indicates that simultaneous scheduling request transmission is allowed. In other modalities of the second method, the mobile communication network can define simultaneous scheduling request transmission as being allowed.
[0125] In some embodiments, the second method also includes determining whether an amount of transmission power is sufficient to simultaneously transmit messages for the first random access procedure and the first parallel scheduling request message. In such embodiments of the second method, transmitting the first escalation request message to the second radio carrier may include reducing the power of a message from a lower priority to the first
Petition 870190113318, of 11/05/2019, p. 68/86
56/58 radio bearer and the second radio bearer.
[0126] In several modalities of the second method, the second radio carrier is not configured with any PUCCH resource for the first scheduling request message. In such modalities, transmitting the first escalation request message comprises initiating a second random access procedure. In some embodiments, the second method includes receiving a temporary storage status report grant for a temporary storage status report in response to the first escalation request message and transmitting uphill link data in the storage status report grant temporary.
[0127] In some embodiments, the second method includes receiving a backoff indicator message, the backoff indicator message including a service identifier field and starting a backoff timer for a specific service for an amount of time based on the indicator message backoff. In various embodiments of the second method, the backoff indicator message includes a plurality of service identifier fields. In certain modalities, the backoff indicator is applied to each service identified in the plurality of service identifier fields. In other modalities, the backoff indicator is applied to all services except those identified in the plurality of service identifier fields.
[0128] A third method for handling multiple UL access procedures is disclosed in this document. The third method includes receiving an activation for a
Petition 870190113318, of 11/05/2019, p. 69/86
57/58 first random access channel (RACH) request, while a second RACH procedure is pending and identifies a first priority of the first RACH request and second priority of the second RACH procedure. The third method also includes transmitting the first RACH request before the completion of the second RACH procedure in response to both the first priority and the second priority being high.
[0129] In certain embodiments, the third method includes aborting the second RACH procedure in response to the first priority being high and the second priority being low and delaying transmission of the first RACH request until completion of the second RACH procedure in response to the first priority being less than the second priority.
[0130] In certain modalities of the third method, the first RACH request is a request for a system information block (SIB), where a request to a SIB has a higher priority than that of another type of RACH request. In certain embodiments of the third method, the first priority and the second priority have the same priority level, where transmitting the first RACH request comprises transmitting during a next RACH opportunity before receiving a response to the second random access procedure. In certain embodiments of the third method, transmitting the first RACH request comprises simultaneously transmitting a first RACH preamble corresponding to the first RACH request and a second RACH preamble corresponding to the second pending RACH procedure.
[0131] In some modalities, the third method
Petition 870190113318, of 11/05/2019, p. 70/86
58/58 includes receiving a first RACH response corresponding to the first RACH request and a second RACH response corresponding to the second RACH procedure, each RACH response including a RACH grant, in which the RACH grants overlap over time. In such embodiments, simultaneously transmitting the first RACH preamble and the second RACH preamble comprises reducing the transmission power of a third RACH message to a lower priority of the first RACH request and the second RACH procedure. In one embodiment, the third method includes reducing the transmission power of a retransmission opportunity from the lowest priority of the first RACH request and the second RACH procedure. In certain embodiments, a power reduction amount of the third message is based on a weighting factor, the weighting factor being selected based on the relative priority of the first priority compared to the second priority.
[0132] Modalities can be practiced in other specific ways. The described modalities should be considered in all aspects only as illustrative and not restrictive. The scope of the invention, therefore, is indicated by the appended claims instead of the previous description. Any changes that arise within the meaning and equivalence range of the claims must be included in its scope.

权利要求:
Claims (20)
[1]
1. Method, characterized by the fact that it comprises:
initiate, by a remote unit, a first random access procedure for a first radio carrier;
receive, on the remote unit, an escalation request activation for a second radio carrier while the first random access procedure remains pending;
determine whether simultaneous escalation request transmission is allowed; and transmitting, by the remote unit, a first scheduling request message to the second radio carrier to a mobile communication network in response to the simultaneous scheduling request transmission being allowed.
[2]
2. Method according to claim 1, characterized in that determining whether simultaneous scheduling request transmission is allowed comprises identifying a logical channel priority associated with the second radio carrier.
[3]
3. Method according to claim 2, characterized by the fact that it additionally comprises comparing the logical channel priority associated with the second radio carrier to a first priority threshold, in which simultaneous scheduling request transmission is allowed if the logical channel priority exceeds the first priority threshold.
[4]
4. Method according to claim 1,
Petition 870190113318, of 11/05/2019, p. 72/86
2/6 characterized by the fact that determining whether simultaneous scheduling request transmission is allowed is based on a configuration of the second radio carrier.
[5]
5. Method, according to claim 1, characterized by the fact that the mobile communication network defines simultaneous scheduling request transmission as being allowed.
[6]
6. Method according to claim 1, characterized in that it further comprises determining whether an amount of transmission power is sufficient to simultaneously transmit messages for the first random access procedure and the first parallel scheduling request message, in response to simultaneous escalation request transmission being permitted, wherein transmitting the first escalation request message to the second radio carrier comprises reducing the power of a lower priority message from the first radio carrier and the second radio carrier .
[7]
7. Method, according to claim 1, characterized by the fact that it additionally comprises:
determining a first logical channel priority of the first radio bearer and a second logical channel priority of the second radio bearer in response to simultaneous scheduling request transmission not being allowed; and canceling the first random access procedure in response to the first logical channel priority being less than the second logical channel priority.
Petition 870190113318, of 11/05/2019, p. 73/86
3/6
[8]
8. Method, according to claim 1, characterized by the fact that the second radio carrier is not configured with any physical channel link control (PUCCH) resource for the first escalation request message, in which transmitting the first escalation request message comprises initiating a second random access procedure.
[9]
9. Method, according to claim 1, characterized by the fact that it additionally comprises: receiving a temporary storage status report grant for a temporary storage status report in response to the first escalation request message; and transmit uplink data in the temporary storage status report grant.
[10]
10. Method, according to claim 1, characterized by the fact that it additionally comprises:
receive a backoff indicator message, the backoff indicator message including a service identifier field; and start a backoff timer for a specific service for an amount of time based on the backoff indicator message.
[11]
11. Method, according to claim 10, characterized by the fact that the backoff indicator message includes a plurality of service identifier fields, in which the backoff indicator is applied to each identified service in the plurality of service identifier fields services.
Petition 870190113318, of 11/05/2019, p. 74/86
4/6
[12]
12. Method, according to claim 10, characterized by the fact that the backoff indicator message includes a plurality of service identifier fields, in which the backoff indicator is applied to all services except those identified in the plurality of fields service identifiers.
[13]
13. Device, characterized by the fact that it comprises:
a transceiver that communicates with a mobile communication network using a plurality of radio carriers; and a processor that:
initiates a first random access procedure for a first radio carrier;
receives an escalation request activation for a second radio carrier while the first random access procedure remains pending; and determines whether simultaneous escalation request transmission is allowed, wherein the transceiver transmits a first escalation request message to the second radio carrier in response to simultaneous escalation request transmission being allowed.
[14]
14. Apparatus according to claim 13, characterized in that determining whether simultaneous scheduling request transmission is allowed comprises the processor identifying a logical channel priority associated with the second radio carrier, in which scheduling request transmission Simultaneous is allowed if the logical channel priority exceeds one
Petition 870190113318, of 11/05/2019, p. 75/86
5/6 priority threshold.
[15]
15. Apparatus according to claim 13, characterized by the fact that the processor uses a configuration of the second radio carrier to determine whether simultaneous scheduling request transmission is allowed.
[16]
16. Apparatus, according to claim 13, characterized by the fact that the mobile communication network defines simultaneous scheduling request transmission as being allowed.
[17]
17. Apparatus according to claim 13, characterized by the fact that the processor additionally:
determines a first logical channel priority of the first radio bearer and a second logical channel priority of the second radio bearer in response to simultaneous escalation request transmission not being allowed; and cancels the first random access procedure in response to the first logical channel priority being less than the second logical channel priority.
[18]
18. Apparatus according to claim 13, characterized by the fact that the transceiver receives a backoff indicator message, the backoff indicator message including a service identifier field, in which the processor starts a backoff timer for a service specific amount of time based on the backoff indicator message.
[19]
19. Apparatus, according to claim 18, characterized by the fact that the message indicating
Petition 870190113318, of 11/05/2019, p. 76/86
6/6 backoff includes a plurality of service identifier fields, in which the backoff indicator is applied to each service identified in the plurality of service identifier fields.
[20]
20. Method, characterized by the fact that it comprises:
initiate, by a remote unit, a first random access procedure for a first radio carrier;
receive, on the remote unit, an escalation request activation for a second radio carrier while the first random access procedure remains pending; and transmitting, by the remote unit, a first escalation request message to the second radio carrier to a mobile communication network before completing the first random access procedure.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112019023263A2|2020-05-26|TRANSMIT SR BEFORE COMPLETING RACH

---

US10841929B2|2020-11-17|Mapping an access attempt type to a network configuration

---

US11272565B2|2022-03-08|Configuration information for an inactive state

---

BR112019022214A2|2020-05-12|DUPLICATION OF PDCP PDUS TO A RADIO CARRIER

---

CN112219413A|2021-01-12|V2X communication over multiple radio access types

---

US10986667B2|2021-04-20|Random-access procedure for scheduling request

---

KR20200087769A|2020-07-21|Fallback Assistance

---

US20200235898A1|2020-07-23|Autonomous bandwidth part switching

---

US20200146045A1|2020-05-07|Preempting an allocation of uplink resources

---

US20200092727A1|2020-03-19|Integrity protection for a packet data unit

---

US20200205090A1|2020-06-25|Reporting power headroom

---

US20200305169A1|2020-09-24|Multiple resource allocation mode configurations

---

US20200351409A1|2020-11-05|Validity information conditions

---

EP3925245A1|2021-12-22|Selectively deactivating a bandwidth part

---

WO2021062585A1|2021-04-08|Method and device for guarantee high qos service via multiple resource pools for nr v2x

---

US20200305055A1|2020-09-24|V2x communication resource for mobility event

---

WO2021152514A1|2021-08-05|Preventing transmission when switching an active uplink bandwidth part

---

WO2021084516A1|2021-05-06|Uplink lbt failure for the active bwp

---

WO2021059245A1|2021-04-01|Scell beam failure recovery

---

CN113273293A|2021-08-17|Determining uplink grants for multiple modes

---

WO2021059089A1|2021-04-01|Determining data transmission preemption

---

WO2021094843A1|2021-05-20|Enabling on-demand system information requests

同族专利:

---

公开号 | 公开日

---

EP3620020A1|2020-03-11|

---

US20180324867A1|2018-11-08|

---

EP3620020B1|2021-03-31|

---

KR20200003804A|2020-01-10|

---

WO2018204922A1|2018-11-08|

---

US10785802B2|2020-09-22|

---

CN110495243A|2019-11-22|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

GB2461158B|2008-06-18|2011-03-02|Lg Electronics Inc|Method for performing random access procedures and terminal therof|

---

US20100232364A1|2009-03-16|2010-09-16|Chia-Chun Hsu|Method of handling random access procedure and related communication device|

---

EP2244515A1|2009-04-23|2010-10-27|Panasonic Corporation|Logical channel prioritization procedure for generating multiple uplink transport blocks|

---

CN102055700B|2009-10-28|2015-06-03|中兴通讯股份有限公司|Method and device for CC configuration in CA|

---

JP5382146B2|2010-02-12|2014-01-08|富士通株式会社|Wireless communication apparatus, wireless communication system, and wireless communication method|

---

JP4945652B2|2010-03-29|2012-06-06|シャープ株式会社|Mobile station apparatus, base station apparatus, radio communication system, random access method, and integrated circuit|

---

EP2633734B1|2010-10-29|2019-07-24|Samsung Electronics Co., Ltd|Method and apparatus for handling in-device co-existence interference in a user equipment|

---

KR101776873B1|2011-01-11|2017-09-11|삼성전자 주식회사|Method and apparatus for setting uplink transmission power in mobile communication system|

---

US9125218B2|2011-09-16|2015-09-01|Htc Corporation|Method of handling random access procedure on primary cell when random access procedure on secondary cell is ongoing or about to start|

---

CN104186010B|2012-03-16|2018-09-21|交互数字专利控股公司|Random access procedure in wireless system|

---

US9407302B2|2012-12-03|2016-08-02|Intel Corporation|Communication device, mobile terminal, method for requesting information and method for providing information|

---

US9974090B2|2013-07-03|2018-05-15|Interdigital Patent Holdings, Inc.|EPC enhancements for proximity services|

---

CN105594141B|2013-08-27|2019-07-05|三星电子株式会社|Method and system for the random access procedure between eNB in carrier wave polymerization|

---

US20150230135A1|2014-02-10|2015-08-13|Qualcomm Incorporated|Inter radio access technology cellular handover|

---

CN107211416B|2015-01-28|2021-08-31|夏普株式会社|Terminal device, base station device, integrated circuit, and communication method|

---

CN107690766B|2015-07-17|2021-03-16|英特尔Ip公司|NB-PRACH sending and receiving device for cellular Internet of things|

---

US20170290042A1|2016-04-05|2017-10-05|Qualcomm Incorporated|Scheduling request transmission to request resources for a buffer status report|

---

US11234273B2|2016-08-12|2022-01-25|Qualcomm Incorporated|RACH conveyance of DL synchronization beam information for various DL-UL correspondence states|

---

WO2018063200A1|2016-09-29|2018-04-05|Intel IP Corporation|Mobile terminal devices and methods in mobile communication devices|

---

WO2018072844A1|2016-10-21|2018-04-26|Nokia Technologies Oy|Random access for nr|

---

US11019652B2|2017-05-04|2021-05-25|Ofinno, Llc|Parallel scheduling request process management|

---

US10524294B2|2017-05-04|2019-12-31|Ofinno, Llc|Scheduling request transmission|

---

CN111386747A|2017-12-20|2020-07-07|联想（新加坡）私人有限公司|Random access procedure for scheduling requests|

---

US11089651B2|2018-04-06|2021-08-10|Apple Inc.|Systems and methods for physical random access channel transmissions|

---

US10849165B2|2018-04-06|2020-11-24|Mediatek Inc.|Handling of simultaneous transmission of PRACH and other uplink channels in mobile communications|US10485017B2|2017-05-30|2019-11-19|Htc Corporation|Device and method of handling a schedule request|

---

KR102055061B1|2017-06-08|2019-12-11|아서스테크 컴퓨터 인코포레이션|Method and apparatus of multiple srconfigurations in a wireless communication system|

---

WO2018230993A1|2017-06-15|2018-12-20|Samsung Electronics Co., Ltd.|Method and apparatus for performing scheduling request to support plurality of services efficiently|

---

KR20190006287A|2017-07-10|2019-01-18|삼성전자주식회사|Method and apparatus for configuring multiple scheduling request|

---

US10887939B2|2017-08-10|2021-01-05|Comcast Cable Communications, Llc|Transmission power control for beam failure recovery requests|

---

US10855359B2|2017-08-10|2020-12-01|Comcast Cable Communications, Llc|Priority of beam failure recovery request and uplink channels|

---

US10887903B2|2017-10-26|2021-01-05|Ofinno, Llc|Wireless device processes with bandwidth part switching|

---

CA3024596A1|2017-11-16|2019-05-16|Comcast Cable Communications, Llc|Beam paging assistance|

---

EP3509373A1|2018-01-09|2019-07-10|Comcast Cable Communications LLC|Beam selection in beam failure recovery request retransmission|

---

CA3033533A1|2018-02-09|2019-08-09|Ali Cirik|Beam failure recovery procedure in carrier aggregation|

---

AU2018414649A1|2018-03-22|2020-10-15|Guangdong Oppo Mobile Telecommunications Corp., Ltd.|Random access method and terminal device|

---

US10772119B2|2018-03-30|2020-09-08|Ofinno, Llc|Scheduling request based beam failure recovery|

---

US10904940B2|2018-03-30|2021-01-26|Comcast Cable Communications, Llc|Configuration for beam failure recovery|

---

US10833753B2|2018-03-30|2020-11-10|Ofinno, Llc|Radio beam failure recovery procedure timing|

---

EP3557778A1|2018-04-02|2019-10-23|Comcast Cable Communications LLC|Beam failure recovery|

---

EP3567776B1|2018-05-10|2021-08-18|Comcast Cable Communications, LLC|Prioritization in beam failure recovery procedures|

---

EP3609285B1|2018-08-09|2021-10-06|Comcast Cable Communications, LLC|Resource management for beam failure recovery procedures|

---

US11051319B2|2018-09-04|2021-06-29|Qualcomm Incorporated|Techniques for low latency communications in wireless local area networks|

---

EP3874865A1|2018-11-01|2021-09-08|FG Innovation Company Limited|Method and apparatus for handling bwp switching in random access procedure|

---

US10925093B2|2018-11-13|2021-02-16|Mediatek Singapore Pte. Ltd.|Method and apparatus for detecting consistent listen before talk failure in mobile communications|

---

CN111432432A|2019-01-10|2020-07-17|华为技术有限公司|Data transmission method and device|

---

WO2020164035A1|2019-02-14|2020-08-20|Qualcomm Incorporated|Prioritization of random access procedures|

---

CN112153725A|2019-06-28|2020-12-29|华为技术有限公司|Wireless communication method, device and system|

法律状态:
2021-10-19| B350| Update of information on the portal [chapter 15.35 patent gazette]|

优先权:

---

申请号 | 申请日 | 专利标题

---

US201762501902P| true| 2017-05-05|2017-05-05|

---

US62/501,902|2017-05-05|

---

PCT/US2018/031420|WO2018204922A1|2017-05-05|2018-05-07|Transmitting sr prior to completing rach|

---